Skip to content

Conversation

yashodipmore
Copy link

Notes for Reviewers

This PR fixes #999

This PR improves the npm link instructions in the README by adding a detailed, developer-friendly, and accurate workflow for contributors to test their local Sistent fork within Meshery or other projects.

Signed commits

  • Yes, I signed my commits.

@leecalcote
Copy link
Member

Thanks, @yashodipmore !

@leecalcote leecalcote requested a review from M-DEV-1 June 26, 2025 19:22
@leecalcote
Copy link
Member

@M-DEV-1 will you review?

# Expected output:
# node_modules/@sistent/sistent -> ../../../../../sistent
```bash
npm ls -g --depth=0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @yashodipmore, wouldn't it be better to not specify the --depth flag here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

depth should equal 1

Comment on lines -174 to -175
> [!NOTE]
> Avoid using `type any` in your code. Always specify explicit types to ensure type safety and maintainability.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert this back, as this is a general tip, not related to local sistent forks.

@M-DEV-1
Copy link
Member

M-DEV-1 commented Jun 26, 2025

@yashodipmore, the DCO check is failing, please signoff your commits.

Ref: https://github.com/layer5io/sistent/pull/1082/checks?check_run_id=44296640731


1. Create a link of your local Sistent fork
The `npm link` workflow allows contributors to test their local changes in Sistent within projects like Meshery UI without publishing the package to npm. It creates a symbolic link from the global `node_modules` to your development version of Sistent, enabling fast feedback during development.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This description, of the npm link command is helpful, but I'm not sure what is new in this change, except this description, and the extra tips in the end. Could you explain maybe why you felt this change was necessary?

Co-authored-by: mahadevan <[email protected]>
Signed-off-by: Rian the rizzler <[email protected]>
@leecalcote leecalcote requested a review from aabidsofi19 August 6, 2025 20:33
@vr-varad
Copy link
Contributor

vr-varad commented Sep 1, 2025

@yashodipmore The Dco Check is failing mind fixing it.

Copy link

github-actions bot commented Sep 1, 2025

🚨 Alert! Git Police! We couldn’t help but notice that one or more of your commits is missing a sign-off. A what? A commit sign-off (your email address).

To amend the commits in this PR with your signoff using the instructions provided in the DCO check.

To configure your dev environment to automatically signoff on your commits in the future, see these instructions.


        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Docs] update readme to include instructions to use npm link
5 participants